Yes, the filter is a touchy matter, but as always it depends on settings. On every text first character replacements are applied, by default all spaces and punctuations are removed, but you may change that. If you leave spaces in text, no one would be warned/kicked for unlucky combination of words, but also the filter would not capture e.g. "shi t". So it is a trade-off. Basically, too short and general words like "con" cannot be defined, it is a far too common combination of letters.
True it is hard to satisfy every need, but maybe the AllowJoining item is too general and should be split into two, one for applying required ranks-licences, one for other limits like time lock or limited joining. I guess car restrictions should be always applied, without questions.
Well, yes, only the 2.2.9 config files are missing some items added later. You'll find all such items mentioned in changelog, it is also good and fast to compare your present config files with the current default ones to see any differences.
No, that would not work. First, all custom cars must have only 3 characters, e.g. UFB, not 5 like you have. So these entries would be correct:
CustomCars=UFB|UFR,45,0
CarGroups=UFB+UFR
But groupinig UFB and UFR is strange, because this is used for approx. equal cars that may compete together, which is not the case of UFR and UFB. Same for CarCategories, they are used for grouping cars into categories usable in commands like !sb and similar, such as !sb gtr or !sb tbo.
First, limiting cars per points/ranks is really a FULL version feature. Second, you're right under one Airio this scheme is not currently possible, because rank is derived from total points of any track/car combination. This is a known issue, I'm currently trying to come with some scheme to allow the limitation you suggest, allowing one kind of cars based on points gained in another group of cars. When it is implemented (say in one or two weeks), it will very probably still be a FULL version feature.
In CFG file find item AllowJoining and set it to 6. It would mean only limads of level 6 will be able to always join races, regardless of restrictions and other limits. And there are no limads level 6 in Airio, level 5 is currently maximum.
Points and other data (lap time, race time, drift score, podiums, later also starts/finishes, maybe also average time) for each driver and track/car combination is stored on two levels called total (which should be never erased) and champ (by default erased once a week).
Commands displaying the data always have two forms plus alternates, such as !ptt (points total, !total) and !ptc (points champ, !champ), !btl (best total lap or !laps), !bcl (best champ lap time or !lap), !btr (best total race time or !races), !bcr (best champ [last week] race time, !race), etc...
Yes, if you delete total stats, nobody will have any points, no ranks, so do not do it. If you want some time-limited competition, use the champ level, erased by !clrc command.
By setting DaysChamp=30 the champ data will be erased every 30th day, regular monthly erase is not supported this way, only scheduled commands may be used for that. But monthly erasure is best done manually, you'll also have a chance to capture the results e.g. as screen shots. Ability to export champ results before erasure is also planned, at least in some limited form.
Indeed you're not a lap back, that would not be (realistically) possible. Also Airio has no control over LFSW, I believe you'll see improvement there even if some penalty is applied for cutting. But LFSW data are not absolutely reliable anyway.
Prohibited zones are by default used only at places where cutting creates major troubles, such as on the inside of T1 on BL1, favorite crashers spot and place of many accidents. Restricted zones really only ignore that lap in Airio, they are created to have "clean" times in Airio stats, e.g. when qualifying for some event.
But you're right an option to define zones with penalties would be nice to have, maybe another independent item could be used for that in TCD file with penalties defined on SRV level...
On another note: Airio 2.3.1 is released.
- The FREE version contains << Previous and Following >> buttons allowing easy listing through any multi-page output, such as the help system, !sb, !ptt and similar.
- The FULL version gives limads/admins Kick/Ban/Act buttons in !players and !recent lists, making all the management actions much easier (no !ban typing is necessary now). All such actions require confirmation or some input (such as ban length or its reason). The Act button combines spectating and penalizing.
- There is also a command allowing to cancel approaching race restart/end action, handy sometimes.
You got it right, and even your deductions are very correct. A few notes:
1) "MyCar" must always have only 3 characters, just like all other LFS cars.
2) Indeed if you define a certain restriction in TCD file, it is applied to all servers. The option here is to apply the restriction only for certain tracks, if they are unique for the server where restrictions should be used.
3) The other option is not to restrict the original car, but make it a prohibited car on certain server. This is from default SRV file:
4) You can also use the !/cars command, it is converting custom cars to standard ones and manipulating with the above config item. Say you have UFB defined as a restricted UFR. By typing !/cars UFB only UFR will be available in selection screen, but it will be restricted at the same time, alowing joins only with UFB. If both cars should be available, you type !/cars UFR+UFB.
5) Using restricted cars requires defining additional strong welcome text and similar measures, because people are usually confused, do not read any messages (saying why they were spectated), and generally do not like any restrictions.
6) Very useful is the !cars command (different from !/cars mentioned above), because it summarizes all defined custom cars and car categories.
Hope this helps.
1) "MyCar" must always have only 3 characters, just like all other LFS cars.
2) Indeed if you define a certain restriction in TCD file, it is applied to all servers. The option here is to apply the restriction only for certain tracks, if they are unique for the server where restrictions should be used.
3) The other option is not to restrict the original car, but make it a prohibited car on certain server. This is from default SRV file:
# Car types separated by space that cannot be used on server - string
# You may use this setting e.g. to allow only custom cars to join
# race - when you define UFB, you may restrict joins with UFR here.
ProhibitedCars=4) You can also use the !/cars command, it is converting custom cars to standard ones and manipulating with the above config item. Say you have UFB defined as a restricted UFR. By typing !/cars UFB only UFR will be available in selection screen, but it will be restricted at the same time, alowing joins only with UFB. If both cars should be available, you type !/cars UFR+UFB.
5) Using restricted cars requires defining additional strong welcome text and similar measures, because people are usually confused, do not read any messages (saying why they were spectated), and generally do not like any restrictions.
6) Very useful is the !cars command (different from !/cars mentioned above), because it summarizes all defined custom cars and car categories.
Hope this helps.
1) There's no exact indication when the green lights actualy appear.
2) Car positions including speeds (which would probably be used for the reaction time) are on server updated just 4 or 5 times per second at best, and especially at race start the lags are clearly visible.
=> On server it would be pure chance if your reaction is seen as 0.02 or 0.2 seconds. 
2) Car positions including speeds (which would probably be used for the reaction time) are on server updated just 4 or 5 times per second at best, and especially at race start the lags are clearly visible.
=> On server it would be pure chance if your reaction is seen as 0.02 or 0.2 seconds.
Ah, Neil, you're completely right. And thanks for the league info! Apo, thanks for the notice, our webmaster will look into the issue.
Apo, thanks for the notice, our webmaster will look into the issue. The WR here is actualy Virtual Record, because there's no true UFB WR record available. It is time-adjusted UFR WR.
I believe the settings are OK, best UFB time on your server is a bit worse than virtual UFB WR, but not by much. If you have one day a beter time than WR, just lower a bit the TimeAdjustment value for that track.
Note in the sector times that UFB loses time in sector 2. The same as for tracks applies here: In twisty sectors UFB will lose only a bit, in straight sectors much more comparing to UFR.
Looks OK, but DefaultCar is also good to have defined (maybe on server level), because newly connected just type !sb and get track+UFB listing, which is correct.
One more note: To check the time adjustments are just about correct, type !good which shows good/great split/lap times. The values shown should be close to top UFB server split/lap times, not off by several seconds.
One more note: To check the time adjustments are just about correct, type !good which shows good/great split/lap times. The values shown should be close to top UFB server split/lap times, not off by several seconds.
Good custom car definition, this approach has many advantages. (I think custom cars are one of the coolest Airio features, so I'm glad you're using it.
)DefaultCar definition is OK, UFB is perfectly valid entry. If you use one Airio on one server, it is no problem to define DefaultCar=UFB in TCD file. If one Airio is managing more servers, that definition should be only on one server (in appropriate Airio.srv.x.txt file), so that not all servers use UFB as default car (assigned to each new connection).
Then we have there the restrictions and time adjustments and I'm afraid that's completely wrong and it is my bad example, sorry!
The correct definition should look like this:Track=
Car=UFR
IntakeRestriction=45
AddedMass=0
Track=SO6
Car=UFB
TimeAdjustment=1830
Track=AS1
Car=UFB
TimeAdjustment=1370
Track=AS2
Car=UFB
TimeAdjustment=1900
Track=FE2
Car=UFB
TimeAdjustment=1280
First global UFR restriction is defined, so that everyone is forced to use UFB. Then it is sufficient to define time adjustments only, but for UFB and not UFR! And that's where I was wrong in the earlier example. So sorry...
Yes, there can be quite large differences, because UFB is much slower to accelerate than UFR, has lower max speed, but can take corners at the same speed as UFR. So, on short and twisty tracks, it can be about 10 percent slower, on longer tracks with straights the difference will raise to 20 percent. UFB is simply a different car.
You could settle for some average values, say 1500 (15 percent) or make it track specific, as you have it now. When you have some stats gathered, you can also define track/UFB-specific good/great times and such, but I would say that's possible only when using limited set of tracks.
Thanks for info!
Airio 2.3.0 is released. It is an attempt to consolidate previous development and solve some previous inconsistencies and illogicalities (if such word exists). The changelog is rather extensive this time, and also quite a few items were added to config files. Still I believe config upgrade by comparing your current and new default files will be quick, a question of a few minutes.
The changelog is rather extensive this time, and also quite a few items were added to config files. Still I believe config upgrade by comparing your current and new default files will be quick, a question of a few minutes.- Airio checks have been divided into 2 categories, one basically about joining the race (with limitations such as time, licence, restrictions, ...), the other mostly about actual racing (idling, speeding, chatting, ...). This separation makes it easy to switch server between normal racing and event racing while keeping all race joining limits.
- Commands such as !sb now support case sensitive nickname filtering. The filter is always the last item and starts with *.
- New verbosity levels allow anyone to switch Airio to !silent or !noisy mode, receiving none or all global messages.
- GUI updates consolidate more buttons into one. Try clicking them repeatedly to see what states they support. Unfortunately buttons text was changed as well, so new translations are necessary. It will take some, but hopefully short time to have 2.3 language files.
- Limad system was updated, with configurable levels 0, 2, 4 available in FREE version and levels 1, 3, 5 added to FULL version. Level 4 may be virtual admin, driver without server pass, but with Airio admin commands available. Level 5 in FULL may be super-admin with reserved commands (e.g. !unban).
- The !players command may be made available to everyone, while the !rep command may be disabled.
- Drift summary (total angle, avg. velocity, time, points) may be shown on each drift end. Also some pitboard data may be shown as pitinfo in chat on each lap finish.
- FULL version has dynamic kick/ban voting being turned on/off according to the "strength" of limads on server. The idea is to disable voting in case there are enough people to take care of troubles.
- Other minor updates, improvements, fixes.
Yup, I have a clue.
Activity is not joining race once in some 25 minutes and just sitting in pits or spectating for another 25 minutes. Activity is racing, racing is passing splits and finishing laps (at least Airio thinks that).The inactivity "timer" is reset for everyne on each split. (I had it on lap finish only, but it was not ideal.) So the guy you talk about was connected to server for more than 30 minutes (under default settings) and then was very unlucky that the check run a few seconds before he crossed a split.
It may happen, but only sporadically and only if he did no racing for set time.
Hi! They are car settings, so you'll find it in track/car data file, TCD. Your case is the classic situation where a custom car should be used, UFB = Baby UFR. I'd suggest you do the following changes in TCD file:
By this you say that any UFR joining race with 45 percent intake restriction or higher and 0 added mass or higher will be reported as UFB, custom car. The major advantage is it will be perfectly valid car for Airio with separate stats and everything, just like if it was LFS car. Every commad accepting car type will recognize UFB as valid selection: !pb ufb, !sb ufb, etc...
The next step is to define how much slower this car actually is than his full-force father. It is also good to prohibit entering race with UFRs with lower restriction than 45 percent. Use something like this at some suitable place in TCD file:
The last value is most important; it specifies that UFB is 20 percent slower than UFR, so it is (percentage * 100) to allow fine tuning. Now you need to calculate somehow what the actual values should be, best by comparing lap times with UFR and UFB on several tracks.
If UFR laps are somewhere 150 seconds and UFB times then 170 seconds, you need to enter (170/150 - 1) * 10000 = 1333 (13.33 percent). OK?
Once the correct time adjustment value is found all the required times will be adjusted accordingly, meaning you'll need standard driving to enter stats, good driving to see good times reported, etc. All the above changes can be applied by simple !rld, no Airio restart is (ever) necessary.
CustomCars=UFB|UFR,45,0By this you say that any UFR joining race with 45 percent intake restriction or higher and 0 added mass or higher will be reported as UFB, custom car. The major advantage is it will be perfectly valid car for Airio with separate stats and everything, just like if it was LFS car. Every commad accepting car type will recognize UFB as valid selection: !pb ufb, !sb ufb, etc...
The next step is to define how much slower this car actually is than his full-force father. It is also good to prohibit entering race with UFRs with lower restriction than 45 percent. Use something like this at some suitable place in TCD file:
Track=
Car=UFR
IntakeRestriction=45
TimeAdjustment=2000The last value is most important; it specifies that UFB is 20 percent slower than UFR, so it is (percentage * 100) to allow fine tuning. Now you need to calculate somehow what the actual values should be, best by comparing lap times with UFR and UFB on several tracks.
If UFR laps are somewhere 150 seconds and UFB times then 170 seconds, you need to enter (170/150 - 1) * 10000 = 1333 (13.33 percent). OK?
Once the correct time adjustment value is found all the required times will be adjusted accordingly, meaning you'll need standard driving to enter stats, good driving to see good times reported, etc. All the above changes can be applied by simple !rld, no Airio restart is (ever) necessary.
Yes. We made a good arrangement with Franky of the 500servers and now updates are available very soon after release (withing several hours, usually even faster).
Everyone using the TCAdmin panel must be aware of one issue: The online file edit/save feature unfortunately saves the files always with ANSI encoding. In case you use non-ANSI characters in config files (e.g. in localized messages), this will lead to incorrect display, because Airio expects the data in Unicode (UTF-8) format. Until the issue is solved (by TCAdmin developers), it is best to change configs by uploading new versions from your PC with correct encoding, not by direct online editing.
We made a good arrangement with Franky of the 500servers and now updates are available very soon after release (withing several hours, usually even faster).Everyone using the TCAdmin panel must be aware of one issue: The online file edit/save feature unfortunately saves the files always with ANSI encoding. In case you use non-ANSI characters in config files (e.g. in localized messages), this will lead to incorrect display, because Airio expects the data in Unicode (UTF-8) format. Until the issue is solved (by TCAdmin developers), it is best to change configs by uploading new versions from your PC with correct encoding, not by direct online editing.
I believe you do not have to ask, you may do the upgrade yourself using the control panel Game Updates under Airio service. This update will overwrite only EXE and PDB (debug info) files, you need to change the configuration files yourself. And when going from 2.1.2 to 2.2.9 you in fact must update the config files completely, because there's been one or two major changes to the structure and old files simply won't work. I would suggest to completely remove old configs, upload new ones from downloaded Airio archive and do completely new config (maybe with the help of items in old files). No need to do such complete reconfig with every update, but in your case it might be the best course to be sure you have all items available and at correct places/files.
2.1.2 is OLD, I would strongly suggest updating to the latest version, 2.2.9 with 2.3.0 coming in a few days. It would basically require doing new configuration because old config files are not (mostly) supported anymore. Further updates will be relatively easy, just an option added here or moved there, no major config structure updates are coming.
If I remember correctly, in 2.1.2 there was a separate file for defining filters, Airio.fil.txt (and Airio.fil.x.txt, where x is server number). So look for that file and definitions there. If the file's missing, then Airio uses its harcoded defaults. In any case, update is strongly recommended, many new features were added/improved since 2.1.2...
If I remember correctly, in 2.1.2 there was a separate file for defining filters, Airio.fil.txt (and Airio.fil.x.txt, where x is server number). So look for that file and definitions there. If the file's missing, then Airio uses its harcoded defaults. In any case, update is strongly recommended, many new features were added/improved since 2.1.2...
I'm afraid it is not running anymore, for some months already. It looks we're short of manpower.
Hm, yes, currently. But I see it may not be the best/desirable behavior, because if you want to do an event, you should turn off all checks, but car limitations should still be applied. Of course you can turn off all the other checks individually (maybe using a SET file), still...
So you believe Restrictions need to be checked always, once defined? What other filters belong to this category then, always running unless expressedly and individually turned off? Maybe DriverSetup, CarSetup, ProhibitedCars, Tyres, Passengers, AI.
EDIT: MC, it was a very good note, something I was fighting with earlier. To solve the issue, I updated Airio, separated all checks into 2 categories - basic (car setup, ranks etc.) and advanced (text, speeding, lagging, ...). In normal server, both basic and advanced should run, during event only basic checks should run andthen you'll have correct car setups and only people with sufficient licence can join. No one will be kicked/spectated for speeding, idling etc...
So you believe Restrictions need to be checked always, once defined? What other filters belong to this category then, always running unless expressedly and individually turned off? Maybe DriverSetup, CarSetup, ProhibitedCars, Tyres, Passengers, AI.
EDIT: MC, it was a very good note, something I was fighting with earlier. To solve the issue, I updated Airio, separated all checks into 2 categories - basic (car setup, ranks etc.) and advanced (text, speeding, lagging, ...). In normal server, both basic and advanced should run, during event only basic checks should run andthen you'll have correct car setups and only people with sufficient licence can join. No one will be kicked/spectated for speeding, idling etc...
Last edited by EQ Worry, .
Here are the checks that will NOT run if all additional Airio checks are turned off (using !ch off). Each check can be also turned on/off individually.
Speed, Spin, Position (restricted and limited zones), Idling, Driving (wrong way), Lagging, Flooding, Name (prohibited), Cursing, Name (doubled in stats), Text (numberplate), DriverSetup (ABS, TC), Tyres, Speeding (in pits), Camera (driver view), Address (doubled IP), Cursing, Cars (prohibited types), Licence/Rank/Rating, Lock (lap time), Join (limited count), Skin, Passengers, AI, Restrictions, CarSetup (gears, brake), Inactivity, Time (split/sector). Also races are not auto-restarted.
By omission BlueFlags check will always run, but I corrected the code now, it now belongs to the above category. Seeing this I believe checking Position using limited zones (invalidating good lap times gained by cutting) should always run, I will correct this.
Last edited by EQ Worry, .
Information about fuel level in cars isnt available to server/Airio, so you cannot check/limit that. In FULL version you have the option to define custom number of required pitstops, together with pit windows and pit work that need to be done on the car (tyres changes, refuelled).
Take the lap time licences as stages/phases, you go throught stage 1, then advance to stage 2 etc. Currently there's no command to sort drivers per completed laps.
I jumped in at your server and I believe the licences are working correctly for you. Lowest level is 1, highest may be anything you define, in your case it is 6. The licences are shown from 6th level (best) to 1st level (worst) intentionally.
Hm, interesting idea, not possible currently. But generally having the option to assign special text to certain usernames sounds cool. I'll put it on my TODO list...
LOL, wrong format, unban reasons are not supported.
The command would try to remove EQ Worry "For realy fast service" from the list and at that it will fail miserably. I mean it will report there's no such username on the ban list. Aaaaahhh, that's good to hear! Airio should capture all online bans, whether you use !ban or /ban command or the admin buttons or priority votes or Airio itself. All such cases will be converted into Airio bans. The only situation Airio cannot catch and convert is using admin /ban command on someone offline, that would result in simple LFS ban.
I'd suggest to request all admins to use only !ban commands, with reasons specified for any longer bans. Still, the offline /ban command can be put to a good use, if you have someone you simply do not want to see connected, even for a split second...
Ouch?
So if I understand it correctly, it is in principle filtering the !top output, but not by some filter specified directly, but by a pre-set usernames, right? Now I wonder what usernames you'll put there. Maybe team members, but then it would be simpler use a filtering by team tag, will it not?
Anyway, I'll see what can I do about implementing general filtering of !sb, !tb and other commands by e.g. team tags, then it will be the time to consider using predefined lists, when I see some point in that.
@ Michele - Uhm, sorry, I do not know what Lapper's !topqual command does. By the look it should display qualification results, but I guess I'm dead wrong here. OK, I'll do some research, hop on to a Lapper server, or you can elaborate, give some example.
@ JustForFun -No problem at all, it is sometimes hard to track the cause of troubles, things double and tripple checked.
@ Unknown -There was a post about one very strange error, something about WebException and wrong state of object, but I can't find the post anymore (or am I simply blind?). I would hope it was some kind of strange system state, I really do not know what could cause it. If it repeats, cause and solution needs to be found...
@ JustForFun -No problem at all, it is sometimes hard to track the cause of troubles, things double and tripple checked.
@ Unknown -There was a post about one very strange error, something about WebException and wrong state of object, but I can't find the post anymore (or am I simply blind?). I would hope it was some kind of strange system state, I really do not know what could cause it. If it repeats, cause and solution needs to be found...
Update sent, lets see if we'll get closer to the target.
Right, you'll find the command format in !lhelp output, but it looks like this:
!ban [time] name ["reason"]
Time (ban length) and reason are optional, but the time (0 = 12 hours, 1 = one day, just like in LFS) must be before name, not the other way, and the reason must start by ", it is a character separating username from additional text. Example:
!ban 3 el_bitcho "Being a really big mouth"
Sorry, Bitcho.
FGED GREDG RDFGDR GSFDG